Schedule List ViewGrid View

Neal Ford offers a new perspective on evolving architecture, showing you how to make “evolvability” a first-class “-ility” in your software projects. Read more.

Agility is impossible if you're fighting your code to make small changes. Agile-friendly architectures are designed to evolve incrementally; you can't be truly Agile if you're not using them. Join Allen Holub to learn how to create systems that are incremental, flexible, and business focused and that easily evolve as you accommodate new requirements—architecture that is ideal for microservices. Read more.

Join Vaughn Vernon to explore the foundational architectures on which today's software is reliably built and the advanced architecture patterns that are necessary for distributed, reactive microservices software. You'll get hands-on experience with the essential strategic and tactical tools for domain-driven design and the architectures and patterns used to develop contemporary advanced systems. Read more.

CNN recently rated software architect the number one job in America. Yet no clear path exists for moving from developer to architect. Mark Richards blends lecture and hands-on real-world group exercises to explore the many aspects of software architecture. You'll learn various integration styles (and when to use them) as well as patterns to fit various business needs and requirements. Read more.

Enterprises need to deliver better software faster. The microservice architecture has the testability and deployability necessary for DevOps. Chris Richardson walks you through using the microservice architecture to develop your applications, exploring key obstacles you'll face (and how to deal with them) and sharing strategies for refactoring a monolith to a microservice architecture. Read more.

Software engineers usually find themselves changing hard-coded content on the presentation layer, changing a paragraph here and there; that’s difficult to maintain and hard to scale. Now imagine you have to support and apply the same changes on the website and other devices. Edwin Maldonado provides the tools you need to design a reusable information architecture. Read more.

APIs are a necessary ingredient of digital transformation strategies. APIs are developed and evolved in ecosystems of existing APIs and existing guidelines and supporting tools. Erik Wilde and Mike Amundsen provide an analysis and assessment of the state of the API landscape, helping you decide how to allocate resources and make strategic investments for improving your API program. Read more.

With systems like Travis CI, Circle CI, and CodeBuild, we're never more than a few lines of YAML away from a complete continuous delivery pipeline. However, ephemeral build systems constantly recreate the world from scratch, increasing build time and lengthening the CD feedback loop. John Chapin addresses those challenges and shares a reference pipeline using AWS CodePipeline and CodeBuild. Read more.

Communication is not an optional soft skill for architects—it's essential to our success. We can have the most brilliant ideas, but if we're ineffective in communicating their value or if we can't obtain buy-in from our stakeholders, we won't be successful. Seth Dobbs shares a process for effectively shaping and communicating your solutions to different stakeholders. Read more.

Valentina Rodriquez shares a manifest describing a set of principles to design high-quality architectures. If you're planning to change your career or just want to improve your architect skills, join in. Read more.

The next evolution of AI and ML is cloud native, managed platforms, and custom-hardware AI. Noah Gift and Robert Jordan teach you how to use managed AI and ML platforms to create solutions in a fraction of the time as a “roll your own" ML solution. Join in to see how these cloud-managed solution compare so you can pick the right solution for the task at hand. Read more.

A web API, like a website, is a channel into your business domain. Because of its simplicity, REST is the de facto standard for developing web APIs. But translating complex domain behavior to simple REST concepts is not straightforward. Tom Hofte and Marco van der Linden discuss RESTful resource modeling and share practical solutions to bridge the gap between a domain model and a RESTful API. Read more.

Matt McLarty introduces microservice-based enterprise transformation architecture (META), a holistic approach organizations can use to ensure their microservices migration delivers its intended benefits, including hands-on exercises using the Microservice Design Canvas and other artifacts. META addresses the technological, operational, methodological, and cultural aspects of the migration effort. Read more.

As architects, it is our responsibility to effectively guide our teams on the technology journey. Nathaniel Schutta outlines the importance of trade-offs, how we can analyze new technologies, and how we can effectively capture the inevitable architectural decisions we'll make. Read more.

Join Christian Hernandez to learn Kubernetes basics using curl, kubectl, oc, and other command-line tools. You'll discover how to model portable, scaleable, and highly available solutions using open source tools for distributed computing. Read more.

Join Philip Wittrock to learn the fundamentals behind Kubernetes API creation and build your own Kubernetes extension API. You'll cover the fundamentals of defining APIs as resources (e.g., versioning semantics) and implementing APIs as controllers. During the second half, you'll apply the conceptual material as we build our own Kubernetes API for MongoDB from scratch. Read more.

Allen Holub covers the ins and outs of choreographed microservice systems in depth, looking at everything from architecture and implementation details to design techniques. Read more.

Ray Mitchell provides valuable insight on how to move an existing system to an improved architecture while keeping the system up and running during the process. Read more.

There are many good reasons to use a microservices architecture, but there are no free lunches. The advantages of microservices come with added complexity. Teams should happily take on that complexity…provided the application in question benefits from the upside of microservices. Nathaniel Schutta cuts through the hype to help you make the right choice for your unique situation. Read more.

Serverless architecture opens up a world of opportunity for development, providing ease of use while deploying and operating at scale. But this can decrease visibility, making it difficult to see when your environment is misbehaving in terms of throughput, functionality, and performance. Tal Weiss introduces a successful new framework for debugging serverless architecture with real-world examples. Read more.

Modern observability tools offer so much to help keep fresh code, well, fresh. That's great news for greenfield code, but most code sooner or later succumbs to the woes of time and team churn. How do you apply observability to code that hasn't been instrumented since day one? Isobel Redelmeier explains how to use observability to refactor old code. Read more.

When developers start as tech leads or architects, they're often confused about how and where to start. Stefania Stefansdottir walks you through tasks and examples of how to get a team up and running with a new project in an existing ecosystem as well as pitfalls and gotchas to keep in mind. Read more.

Every organization has at least a phalanx or two in the cloud. This is, understandably, changing the way we architect our systems. But your application portfolio is full of heritage systems that hail from the time before everything was as a service. Not all of those applications will make it to the valley beyond, so join Nathaniel Schutta for tips on grappling with your legacy portfolio. Read more.

Vladik Khononov shares an experience report of using the domain-driven design (DDD) methodology at a greenfield company from the first day the company was founded all the way to acquisition by one of his clients. Read more.

Architects provide guiding principles as part of their architecture to enable decision making for unforeseen details but seldom develop guiding principles as leaders and for interacting with people. Seth Dobbs shares a core set of principles that enable effective interactions with your team and your stakeholders. Read more.

The number of microservices running in enterprises increases daily, and service composition, governance, security, and observability are becoming a challenge to implement and incorporate. Asanka Abeysinghe discusses how a cell-based architecture can be applied to current or desired development and technologies to address these issues. Read more.

Service mesh discussions are dominated by vendors trying to frame mesh as a new technology. However, just as microservices are a pattern, not a specific technology, service mesh is a new way to deploy features that API management once comprised. Marco Palladino explores the service mesh pattern, notes the reasons for its emergence, and outlines the technical requirements. Read more.

Join Ryan Kitchens in an introduction to Safety-II concepts that will help move the industry forward, increasing the opportunity for learning from success with some fundamental and practical ways that get us from "Why did things go wrong?" to "How did things go right?" Read more.

Nicolas Brousse and Oleksii Mykhailov found a distributed infrastructure that leverages public cloud providers and a private cloud with open infrastructure can deliver dynamic advertising content with low latency, preserving its high availability in an award-winning paper. Join them as they present their techniques and demonstrate how to design an ad-serving service that is resilient to failure. Read more.

Mandy Waite shares how she and her team at Google Cloud are working to make developers happier and more productive and details how her team uses their internal research and expands upon it to collaborate with Google Cloud partners and open source projects. Join in to get tips on how to cultivate a DevOps culture inside your company. Read more.

Rezaul Hoque outlines the architecture behind the services powering people's experiences in Office 365 (Outlook, SharePoint, and OneDrive). Read more.

Communicating (about) architecture to non-IT/business stakeholders is a valuable skill for architects. After all, many architectural-relevant decisions are made by others, so they need to be informed with clear, honest, intelligible, and actionable information/advice. Jochem Schulenklopper shows theory, examples, and useful tips on eight different facets of visual communication of architecture. Read more.

Software systems have a dynamic nature that requires a design approach different from the architecture of physical structures. Systems thinking examines the structure and behavior of complex systems. Matt McLarty provides an introduction to systems thinking and explores how it can be applied to software architecture, particularly in the context of distributed systems and microservices. Read more.

Architecture standards change in months, not years, bringing new capabilities, but taking advantage of them requires constant monitoring and tight feedback loops. We’ve embraced continuous delivery, but how do we enable continuous evolution? Paula Paul and Cassandra Shum explore architecture as code as a means to enable continuous evolution. Read more.

With the explosion of microservices and Kubernetes, enterprises have recognized the importance of empowering developers to productionize their software. However, most companies still have separate ops/DevOps teams and software teams. Priyanka Sharma investigates why this is the case and explains how tooling and workflows make or break shift left. Read more.

NS1 first developed and operated a SaaS DNS platform, then shifted to releasing versioned software for on-prem use of its DNS products. Renee Orser details the many lessons, including the relationship between system architecture and organizational design, that surfaced while the team managed the challenges brought by diversification of a single platform across a suite of deployment models. Read more.

Often microservices and bounded contexts are considered to be the same thing. They are not. Vladik Khononov identifies the difference between microservices and bounded contexts, provides heuristics when each pattern should be used, and shares his experience optimizing microservices-quotebased architectures at Naxex. Read more.

Patterns are an excellent way of building knowledge of an architectural style. As serverless starts to mature, we're starting to see patterns emerge. Mike Roberts introduces you to some of them and helps you look for patterns in your own organizations. Read more.

Being wrong is often seen as the worst thing that can happen, especially when you build business-critical applications and services. Never before has software owners had such an opportunity, or the power, to be wrong. Russ Miles turns being wrong into a superpower for you and your organization. Read more.

Enterprise organizations are attempting to use managerial mechanisms from previous ages to direct software delivery in this one. The problem is that the principles of modern software-delivery approaches are not translating to the business. Mik Kersten presents the Flow Framework—a new approach to software delivery bridging the gap between business strategy and technology delivery. Read more.

A loosely coupled software architecture and an organizational structure to match is one of the biggest predictors of continuous delivery performance. Nick Tune explains why technical leaders must adopt a sociotechnical mindset to minimize dependencies and maximize team autonomy, optimizing end-to-end value creation and delivery speed. Read more.

Software metrics can be used effectively to judge the maintainability and architectural quality of a code base. Even more importantly, they can be used as canaries in a coal mine to warn early about dangerous accumulations of architectural and technical debt. Alexander von Zitzewitz outlines key metrics that every architect should know and shares a new metric to measure software maintainability. Read more.

How can architects collect and make sense of stories from the tactical frontlines to inform long-term technology strategy and vision? Cat Swetel reviews published time span research and works through what the shorter time spans of Agile and CI/CD may mean for software architecture and sociotechnical systems overall. Read more.

Twilio SendGrid delivers more than 50 billion emails per month from some of the most recognizable brands on the internet. Three years ago, SendGrid began a journey to fully rearchitect its systems to cloud native, as a precursor to public cloud migration. Join J.R. Jasperson to explore the drivers, trade-offs, and technical decisions that enabled SendGrid’s transition to the cloud. Read more.

While most of us think our software designs are based in rational, logical thought, the truth is much scarier. Ian Varley covers the emerging field of cognitive biases—bugs in our mental operating system—and takes a cold, hard look at how these mental blind spots defeat our attempts to build systems that serve our users and stand the test of time. Read more.

Anuar Nurmakanov shares his team’s journey with DDD from the very beginning of a project and outlines the many problems they faced. He then details some anti-patterns to be afraid of and how to deal with them, DDD best practices, and how DDD and microservices ideas can leave together. Read more.

Reactive software development is becoming essential to implementing responsive, resilient, elastic, and message-driven solutions. Vaughn Vernon shows you how, by aligning scale and throughput with business-driven model fluency of your core initiatives, you can achieve critical differentiating competitive advantage. Read more.

Private clouds present many unique challenges to architects and software engineering wishing to build and deploy machine learning solutions. Derek Ferguson and Laura Schornack walk you through a real-world example that addresses these challenges using Kubernetes, TensorFlow, and KubeFlow. Read more.

Event storming offers a way to simultaneously collaborate with businesspeople to understand the problems that the business has to solve and develop an architecture for the solution. Join Allen Holub for an in-depth look at event storming and its underlying concepts (from DDD), as well as an extensive hands-on demo of the process. Read more.

Many presentations on microservices offer a high-level view of the architecture; rarely do you hear what it’s like to work in such an environment. Stephen Pember shares his experience migrating from a monolith to microservices across several companies, highlighting the mistakes made along the way and offering advice. Read more.

Every software system has an architecture. Many are little more than the result of circumstances, rather than deliberate decisions. Helping teams think about software architecture is a key to helping them grow well. James Thompson demonstrates how to assess approaches and make decisions based on what matters to your team and your projects. Read more.

The resiliency of microservices-based applications heavily depends on how well they handle interservice communication over an unreliable network. Kasun Indrasiri provides an in-depth overview of common microservice resiliency patterns such as timeout, retry, circuit breaker, fail-fast, bulkhead, transactions, and failover/load balancing, and the role service meshes play in realizing them. Read more.

When you’re operating multiple services, outages can feel like murder mysteries. Forensics tools such as monitoring and observability are essential, but it's a challenge balancing priorities between new features and tools to pinpoint root causes. Thomas Rampelberg discusses how Linkerd 2.0 provides many of the tools you need to tame the chaos of operating microservices in a cloud native world. Read more.

Credit card fraudsters are always changing their behavior and developing new tactics. For banks, the damage isn’t just financial; their reputations are on the line. So how do they stay ahead of the crooks? Sarah LeBlanc and Hany Elemary explore a system that utilizes continuous delivery for machine learning to allow for rapid experimentation and the deployment of models to catch these fraudsters. Read more.

After an expensive failed attempt at a complete rewrite, Ticketmaster is attempting to evolve the monolith that is its core ticketing platform. Cat Swetel isn't talking about best practices for DevOpsing your monolith; she tells the true story of one company’s journey toward a more flexible, adaptable, and easily maintainable architecture using tools like Wardley Maps and real options theory. Read more.

We have a choice in designing our careers: follow the path of a technologist, exploiting a tech, or become a computational thinker who can address a much broader set of problems. Sarah Aslanifar compares the human mind to a computer, discusses ways to build intuition for your code, and teaches you some techniques to learn more efficiently and retrieve information more quickly. Read more.

How do you effectively select and integrate infrastructure technologies for cloud-based microservice architectures, especially technologies for persisting and moving data? Jeff Carpenter walks you through the proper usage of various styles of databases, caches, and streaming solutions and effective patterns for combining these technologies, using Apache Cassandra and Apache Kafka as examples. Read more.

The growing number of commercial and open source satellite imagery datasets is enabling remote sensing data for industrial applications. Alex Kudriashova walks you through designing and building an entire processing infrastructure and discusses its challenges, like infrastructure scalability, large frame size, data accessibility and latency, and cross-calibration between the data sources. Read more.

Tim Bonci explores how we're going to automate all the things, reduce toil, make our systems smarter and recover automatically, except sometimes you're automating a house of cards built on the back of individual people and a well-meaning solution can fail to address the true problems in the system. Read more.

Tammy Butow accelerates your understanding of how your network can break (packet loss, blackhole attacks, latency injection, and packet corruption) and impact your services. Read more.

The ecosystem in which we are building our solutions is rapidly growing, and it's challenging to make the right decisions and keep track of the expanding options. Lena Hall and Adron Hall share solution architecture best practices for distributed cloud native systems. Find answers to hard questions to help design failure-proof, manageable, flexible, ready to adjust to future changes systems. Read more.

How can you reliably improve and refactor serverless applications? How do you ensure you have covered all the unexpected edge cases that occur in production? Gero Vermaas and Jochem Schulenklopper explain and demonstrate a scientific approach (promoted by GitHub in its Scientist library) that enables you to release refactored serverless applications to production with great confidence. Read more.

Is security always a bolt-on in your software process? Is your secure development lifecycle "build, then duct-tape on some security"? Wendy Knox Everette explains why good design principles go hand in hand with a strong security stance and highlights the importance of designing in security from the very start of your development process. Read more.

Containers have become the new standard to build cloud native microservice-based applications, and organizations are leveraging service meshes to solve common issues like service discovery, traffic management, circuit breaking, telemetry, fault injection, and more. Join Samir Behara to go beyond the buzz and understand microservices and service mesh technologies. Read more.

John Chapin explains how—in this brave new world of managed services and platforms—you can use serverless technologies and an infrastructure-as-code mind-set to architect, build, and operate resilient systems that survive even massive vendor outages. Read more.

Testing microservices can be hard as they’re often coupled together through APIs or messaging. This can lead to too much reliance on slow end-to-end testing or unreliable unit tests caused by inaccurate stubs of other microservices. Andrew Morgan offers an overview of the consumer-driven contract testing technique, a TDD approach at the API level that aims to mitigate these problems. Read more.

A free puppy is great but also takes a lot of time, energy, and money. Likewise, when we make a build-versus-buy calculation, it's easy to miss several important parts of the calculation, including maintenance, updating, security, availability, and finding operators. None of those are easy to articulate or value for either side. Join Heidi Waterhouse to learn why business value is more than money. Read more.

An application gateway is a piece of infrastructure that helps existing software systems incrementally adopt new technologies like microservices and serverless. It's not as single purposed as an API gateway and not as complicated as a full-service mesh and provides immediate value. Christian Posta explores this emerging pattern. Read more.

There are two common architectural failure modes: hierarchical command and control from ivory-tower architects with strict approvals and rigorous control gates, and chaos with every team doing what they want with little governance. Jonny LeRoy explores the Goldilocks zone that ensures that teams handle organizational risks and opportunities while giving themselves as much autonomy as possible. Read more.

Jeff Beck has been on a five-year journey evolving the architecture at SmartThings, moving from one monolith and three supporting services to more than one hundred microservices and expanding from a US-only platform to a worldwide IoT platform. The architecture has been shaped by product and organizational needs. Join Jeff to explore the major architectural eras iterated on the platform. Read more.

Machine learning is changing the world. Andrew Bonham and Thiagarajan Subramanian demonstrate how to use a reactive microservice architecture style with machine learning and Akka to build a next-generation business process, including a live demo that implements this pattern on AWS using an H20 model for machine learning, Kafka, Akka-based microservices, and Lagom. Read more.

One of the main issues with deploying deep learning solutions is finding the right way to operationalize models within the company. The serverless approach for deep learning provides cheap, simple, scalable, and reliable architecture. Rustem Feyzkhanov shows you how to deploy the TensorFlow model for image captioning on AWS infrastructure. Read more.

OpenCensus is a new standard for tracing and metrics of cloud services, used for observability into applications that span multiple clouds and technological stacks. Simon Zeltser explains how to use vendor-agnostic client libraries for OpenCensus to export telemetry to common distributed tracing systems and covers core concepts like tags, metrics, exporters, zPages, and context propagation. Read more.

Most organizations want faster, more-incremental delivery of their applications, but fragile tests and complex continuous delivery pipelines often make this difficult. What if the problem isn’t the pipeline but the architecture of the system? Ken Mugrage details the architectural choices that will help you enable stable tests and faster pipelines. Read more.

Eric Brewer discusses the importance of Istio and its role in shaping the future of microservices management by offering a more secure environment, visibility for monitoring, and logs for services. Join in to explore Istio and learn how the project is optimized to work with on-premises and cloud infrastructures. Read more.

LN Renganarayana is on a mission to provide strong privacy and security for ML products built with customer data. A key enabler of Workday's mission is an architecture guided by the principles of privacy by design and data protection by default. Interested? Come learn about the design and the trade-offs. Read more.